Displaying targeted website content based on social user profile data

ABSTRACT

Displaying targeted website content based on social user profile data is disclosed. In some embodiments, the displaying of targeted website content based on social user profile data includes requesting social profile data for a user from an authentication provider using a token associated with the user; and generating a rule for web site customization using the social profile data.

BACKGROUND OF THE INVENTION

Various services such as Facebook®, Twitter®, Linkedin®, and others expose service APIs that adhere to various authentication protocols (e.g., OAuth 1.0/2.0, etc.) so that external websites or applications may use such “trusted” services as sources of authorization and authentication (in lieu of, or in addition to, their own internal authentication mechanisms).

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

FIG. 1 is a diagram illustrating an embodiment of an environment in which a system for displaying targeted website content based on social user profile data is used.

FIG. 2 is a block diagram illustrating an embodiment of a web experience management system.

FIG. 3 is a flow diagram illustrating an embodiment of a process for allowing a website to authenticate users based on an authentication protocol.

FIG. 4 is a diagram illustrating an embodiment of an interface for generating a Facebook® application.

FIG. 5 is a diagram illustrating an embodiment of an interface for generating a Twitter® application.

FIG. 6 is a diagram illustrating an embodiment of an interface for a stabling a new group for social users.

FIG. 7A is a diagram illustrating an embodiment of an interface for creating a Facebook® cloud service configuration.

FIG. 7B is a diagram illustrating an embodiment of an interface for creating a Twitter® cloud service configuration.

FIG. 8 is a diagram illustrating an embodiment of an interface for applying cloud service configurations to a website.

FIG. 9 is a flow diagram illustrating an embodiment of a process for displaying targeted website content based on social user profile data.

FIG. 10 is a flow diagram illustrating an embodiment of a process for obtaining social user profile data.

FIG. 11 is a diagram illustrating an embodiment of an interface for logging into an Adobe CQ website using existing digital identities.

FIG. 12 is a diagram illustrating an embodiment of an interface for configuring a client context to display social profile data.

FIG. 13 is a diagram illustrating an embodiment of an interface for configuring a segment.

FIG. 14 is a diagram illustrating an embodiment of an interface for creating a teaser.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.

Various services such as Facebook®, Twitter®, Linkedin®, and others expose service APIs that adhere to various authentication protocols (e.g., OAuth 1.0/2.0, etc.) so that external websites or applications may use such “trusted” services as sources of authorization and authentication (in lieu of, or in addition to, their own internal authentication mechanisms).

Typically, however, it takes a significant amount of time for a developer of a website to implement and test code for each service that they wish to consume as an authentication source. This can make it difficult to retrieve social user profile data from multiple “trusted services” in order to provide targeted content to users. This can be inconvenient.

Thus, there is a need for an improved system that allows a website to take advantage of “trusted” services and effectively use information such as social user profile data obtained from the “trusted” services to display targeted website content.

Accordingly, displaying targeted website content based on social user profile data is disclosed in accordance with some embodiments.

FIG. 1 is a diagram illustrating an embodiment of an environment in which a system for displaying targeted website content based on social user profile data is used. In the example shown, “Bob” (102) is a visitor of the website for the sporting goods store, Geometrixx Outdoors (104), which is published using website experience management (WEM) system (106). In some embodiments, website (104) is an Adobe CQ website and WEM (106) is an Adobe CQ web experience management (WEM) system that is used to author/publish website (104) as well as manage and dynamically determine and deliver personalized content. Website (104) is configured via WEM (106) by administrator (112). In various embodiments, administrator (112) is a website developer, digital marketer, or any other appropriate administrator of website (104). For purposes of illustration, embodiments employing an Adobe CQ web experience management system to author/publish an Adobe CQ website (“Geometrixx Outdoors”) are described in detail below. Other WEM systems or publishing/authoring platforms can also be used.

In some embodiments, services 114 and 116 are digital identity platforms that provide authentication services (e.g., via APIs) such that a member of the platform can log onto and be authenticated by external websites (e.g., Adobe CQ website 104) using their existing digital identities. Examples of such digital identity platforms that provide authentication services include Facebook®, Twitter®, Linkedin®, Foursquare®, and others. The digital identity platforms can each be associated with various authentication protocols (e.g., OAuth 1.0/2.0, etc.) so that an external Adobe CQ website (such as Geometrixx Outdoors 104) and WEM 106 can use such “trusted” platforms as sources of authentication and authorization (e.g., of resources of the trusted sites).

In some embodiments, Adobe CQ system 106 includes an authentication configuration engine 108 that is configured to communicate with services 114 and 116 and allows website 104 to authenticate users based on various authentication protocols. This can enable Bob, for example, to log into the Geometrixx Outdoors website (104) using his existing Facebook® and/or Twitter® digital identities (i.e., federated identity or social login). Adobe CQ system 106 can also be authorized (e.g., by Bob) to obtain resources (e.g., social profile data) from each of services 114 and 116 for providing targeted, personalized content (e.g., as part of a marketing campaign) via social connect engine 110. In some embodiments, information associated with Adobe CQ system 106 is stored in storage unit 118. In various embodiments, storage unit 118 can be a database, flat file, or any other appropriate storage unit.

In some embodiments, the authentication and social connect engines are included as pluggable services (e.g., OSGi services) that can be integrated as part of a website development process on Adobe CQ system 106. As the authentication configuration process is integrated into a website publishing system such as Adobe CQ, connecting with authentication providers such as Facebook® and Twitter® can be simplified in a manner that allows an Adobe CQ website (104) to be automatically configured take advantage of trusted digital identity platforms while minimizing the amount of authentication protocol and coding knowledge (e.g., to handle handshakes, redirects, accessing social profile data, etc.) needed by administrators to implement the authentication and login functionality. Additionally, in some embodiments, other publishing/authoring services such as marketing campaign management services are included on publishing system 106 and are authorized to use information associated with authenticated users that is obtained from digital identity platforms such as services 110 and 112 for providing personalized content to Bob.

In various embodiments, the elements of environment 100 communicate via a network that comprises one or more of a wired network, a wireless network, a local area network, a wide area network, the Internet, or any other appropriate network.

FIG. 2 is a block diagram illustrating an embodiment of a web experience management system. In some embodiments, system 200 of FIG. 2 is used to implement Adobe CQ system 106 of FIG. 1. In the example shown, Adobe CQ system 200 includes authentication configuration engine 202, social connect engine 204, and marketing campaign management engine 206. In various embodiments, engines 202, 204, and 206 comprise, as described above, pluggable services (e.g., OSGi services) that can be integrated into an Adobe CQ system to communicate with each other as well as other services/components that can also be implemented on the Adobe CQ system.

Authentication configuration engine includes authentication handler 208, authentication library 210, and authentication service configurator 212. In some embodiments, authentication handler 208 includes authentication handlers to handle various authentication workflows (e.g., specialized authentication handlers for OAuth 1.0/2.0, etc.). In some embodiments authentication library 210 includes libraries used to implement various authentication protocols/standards and communicate with various APIs (e.g., APIs for Google®, Yahoo®, Linkedin®, Twitter®, Foursquare®, Facebook®, etc.). In some embodiments, software development kits (SDKs) are also included, which can be used by administrators to configure their Adobe CQ websites as trusted authentication providers. For example, an administrator of Geometrixx Outdoors can allow users to create new digital identities and credentials for Geometrixx Outdoors, which can in turn be used to login to other third party websites.

In some embodiments, authentication service configurator 212 is used to configure services that are used to communicate with various authentication providers (e.g., Facebook®, Twitter®, etc.). In some embodiments, an authentication service is configured for each digital identity platform that an Adobe CQ website (e.g., website 104 of FIG. 1) is configured to communicate with and authenticate users. More than one authentication service can also be configured for a single authentication provider (e.g., that includes different settings/configurations).

The authentication services can be configured to include details of applications created at authentication providers, which will be described in more detail below. In various embodiments, service configurations include permissions to be requested of authenticated users, such as credentials (e.g., username and password), resources which an Adobe CQ website such as Geometrixx Outdoors is authorized to access (e.g., Facebook® likes, interests, profile information, friends, Twitter® feeds, followers, etc.) as well as actions that Geometrixx Outdoors can perform on behalf of the user (e.g., post a status update on behalf of a Facebook® user or a tweet on behalf of a Twitter® user). In some embodiments, authentication service configurations include user groups (e.g., CQ authentication user groups) that a visitor can be grouped into based on the digital identity platform that they have logged into the Adobe CQ website with. The user groups (e.g., CQ user groups) can be used by other components of an Adobe CQ system, such as a marketing campaign management component to provide a personalized web experience. In some embodiments, authentication service configurations are associated with, or otherwise applied to, particular portions of an Adobe CQ website or content management system (such as Adobe CQ). For example, Adobe CQ website 104 of FIG. 1 could include an Italian portion of the website, whose Facebook® authentication service is configured differently to the Facebook® authentication service applied to the French portion of the website. For example, the two services, although both associated with Facebook®, could be configured differently and request authorization for access to different resources due to cultural privacy concerns. Different portions of a website can also be associated with different authentication providers as well. For example, if Geometrixx Outdoors is configured to allow a user to login using their Facebook®, Twitter®, and Linkedin® digital identities, the shopping portion of Geometrixx Outdoors could be allowed to have access to Facebook® and Twitter® social profile data, while a “jobs” portion of the website could be allowed to have access to a user's Linkedin® social profile data.

Social connect engine 204 includes client context engine 214 and rule/segment engine 216. Social connect engine 204 can be used to allow users to connect to and manage connections with various digital identity platforms. In some embodiments, client context engine 214 is a content management component configured to read authorized user profile data of the digital identities that a user has logged in with (e.g., Facebook®, Twitter® social profile data) to generate a new profile of the user. The user profile data can then be mapped to a segment (i.e., to segment the user) which will be described in more detail below. In some embodiments, determinations of what content to display or rendered to a user are made based at least in part on the segmenting of the user. The information included in the client context can be used by various components (e.g., marketing campaign management component 206) of a WEM such as Adobe CQ to provide a user with targeted, personalized content. In some embodiments, the client context information is stored or otherwise maintained on the side of the user visiting the Adobe CQ website (e.g., within the browser of the visitor).

Rule/segment engine 216 is configured to facilitate the generation of segments and rules based on user profile data obtained from one or more existing digital identities of authenticated users (e.g., social profile data) and allows the segments and rules to be associated with one another to be interpreted by components such as client context engine 214 and marketing campaign management engine 206. In some embodiments, segments are used to segment the user into a particular bucket in order to provide a visitor, such as Bob, with targeted and personalized content that is maintained in the marketing campaign management section of an Adobe CQ system. In some embodiments, segments are collections of one or more rules/traits. In some embodiments, rules are defined conditions (or traits of interest) associated with or generated from obtained information that when matched or triggered on, can be used to identify users and provide targeted/personalized content. Examples of rules/traits include “gender=male,” “Facebook® like=snow,” “Facebook® interest=snowboarding,” “Twitter® follower of =Shaun White.” Segments can then be generated from defined rules to segment a user into a particular bucket that can be associated with candidate content/experiences. Example candidate content/experiences include teasers/paragraphs to be displayed/rendered (e.g., used to steer specific visitor segments to content that is focused on their interests), newsletters, e-mail communications, content used for testing and targeting (e.g., for use by a marketer as a tool to optimize a website to provide more relevant content and offers by designing and executing tests, creating audience segments, targeting content, etc.), or any other appropriate candidate content/experiences. As an example, a segment including the rules “gender=male,” “like=formula 1,” and “fan of =Ayrton Senna,” can be created, and users who match this segment and collection of rules are shown a particular teaser out of a number of candidate teasers associated with various marketing campaigns (e.g., formula 1 racing teaser instead of hiking teaser).

Marketing campaign management engine 206 is an example component of an Adobe CQ system that can take advantage of integration with authentication engine 202 and social connect engine 204 to dynamically determine and deliver targeted and personalized content (e.g., teaser or ad or customized website) to a visitor such as Bob (i.e., in the context of Bob as a visitor) of an Adobe CQ website who has logged into the Adobe CQ website and been authenticated using existing digital identities such as their Facebook® and Twitter® logins and credentials.

FIG. 3 is a flow diagram illustrating an embodiment of a process for allowing an Adobe CQ website to authenticate users based on an authentication protocol (e.g., OAuth 1.0/2.0, etc.). In some embodiments, process 300 of FIG. 3 is executed by authentication configuration engine 202 of FIG. 2. The process begins at 302 when an authentication package is installed. Packages and code used to implement authentication mechanisms can be installed as a pluggable service (e.g., as pluggable OSGi service) of a web authoring platform (e.g., Adobe CQ). The installed packages can include default packages that are preconfigured to connect with digital identity platforms (e.g., Facebook® or Twitter®) that utilize particular authentication protocols or mechanisms (e.g., OAuth 2.0 or 1.0). The installed packages can also include tools (e.g. SDKs) for developers to configure connections for other digital identity providers.

At 304, an authentication handler is configured to handle the authentication workflow of an authentication provider (e.g., OAuth 1.0 for Twitter®, OAuth 2.0 for Facebook®, etc.).

At 306, an application associated with an authentication provider (e.g., Facebook®, Twitter®, etc.) is generated. In some embodiments, an application is generated in order to make a Adobe CQ website (e.g., Geometrixx Outdoors) known to the authentication provider so that the Adobe CQ website and the authentication provider are connected to allow for authentication, authorization, and exchange of information between the two entities. For example, a properly configured Facebook® application (e.g., via Facebook® connect) enables Facebook® social login and connection. In some embodiments, a user, such as administrator 112 of FIG. 1 is prompted to generate an application at the authentication provider. In some embodiments, one or more keys are provided in response to generating an application. For example, when generating a Facebook® application, an application id and secret are provided.

At 308, a group of users is established. In various embodiments, existing user groups (e.g., CQ user group) can be leveraged or a new user group can be created specifically for users. For example, Facebook® users and Twitter® users can be included in a group called “fbusers” or “Twitter® users,” respectively, or can be included in a general social users group. In some embodiments, all users are included in a general “social users” group.

At 310, a service configuration associated with an authentication provider is generated. The service configuration is set up by an administrator of an Adobe CQ system to enable authentication with a particular authentication provider for which an application has been created. The service configuration includes the details of the application created (e.g., keys), permissions requested (i.e., authorized resources), and the CQ user group to be used for new users who login via the authentication provider. The permissions requested can include basic permissions as well as additional extended permissions that can be specified by the authentication provider as options. Each authentication provider can have a unique and special set of permissions that specifically relate to their digital identity platform.

At 312, a service configuration is applied to a portion of an Adobe CQ website. As described in the example above, if an Adobe CQ website such as Geometrixx Outdoors included French, German, and Italian portions of the website, different credentials and resources could be requested from Facebook® for the French and German site than the Italian site, which would be automatically/dynamically configured and specified by using specialized service configurations/settings while minimizing specialized code development. In some embodiments, portions of the website can also be associated with different authentication providers via service configurations so that a user can use various authentication providers for logging into the website.

FIG. 4 is a diagram illustrating an embodiment of an interface for generating a Facebook® application. In the example shown, an App ID and App Secret (402) are provided for accessing Facebook®. At 404, the website utilizing Facebook® login (e.g., Geometrixx Outdoors) is entered.

FIG. 5 is a diagram illustrating an embodiment of an interface for generating a Twitter® application.

FIG. 6 is a diagram illustrating an embodiment of an interface for establishing a new group for social users (e.g., new CQ User Group for general “socialusers” including Facebook®, Twitter®, Linkedin® users, etc.).

FIG. 7A is a diagram illustrating an embodiment of an interface for creating a Facebook® cloud service configuration. In the example shown, the App ID and Secret provided when generating the Facebook® Application are entered into the Facebook® service configuration. “fbusers” (704) is an example user group (e.g., CQ user group) that authenticated users who login via Facebook® are added to. As described above, the group can be an existing group or a new group that was established via the interface as shown in FIG. 6. Example user permissions (e.g., basic or default permissions) such as “user about me, user activities, user birthday, user interests, user likes, etc.” are shown at 706. Extended permissions are also shown, which may be further requested from a user upon login.

FIG. 7B is a diagram illustrating an embodiment of an interface for creating a Twitter® cloud service configuration

FIG. 8 is a diagram illustrating an embodiment of an interface for applying cloud service configurations to a website. In the example shown, Facebook® Connect and Twitter® Connect cloud service configurations (802) are applied to the Geometrixx Outdoors Site (804) via the interface. Service configurations (with potentially different settings) can also be applied to other portions of the Adobe CQ website, such as the Geometrixx Outdoors mobile site.

FIG. 9 is a flow diagram illustrating an embodiment of a process for displaying targeted website content to an Adobe CQ website visitor based on social user profile data. In some embodiments, process 900 is executed by social connect engine 204 and marketing campaign management engine 206 of FIG. 2. The process begins at 902 when social profile data is requested and received, as will be described in more detail below.

At 904, rules and segments are generated. As described above, rules and segments can be generated using social profile data and used to segment users into various buckets in order to allow for dynamic website customization and to provide targeted and relevant content to users (e.g., as part of a targeted marketing campaign). In various embodiments, generating a segment includes entering a title for the new segment (e.g., “Snowboarders”) and configuring properties of the segment, which can be based on obtained social profile data specifying particular rules or traits of interest. For example, the “Snowboarders” segment can be configured to include generated rules such as “Facebook® interest=snowboarding,” “Favorite Athlete=Shaun White,” etc.

At 906, a segment (and its associated collection of rules) is associated with a campaign. For example, because the winter season is approaching, a digital marketer associated with Geometrixx Outdoors can decide to begin a new marketing campaign associated with winter sports. In creating the new marketing campaign, the digital marketer can create various teasers or banners associated with snowboarding, skiing, etc. In order to provide the appropriate and relevant teaser to a visitor of Geometrixx Outdoors, the digital marketer can associate the snowboarding campaign teaser with the snowboarding segment generated above.

At 908, content is provided to an Adobe CQ website visitor. Using the segments and campaigns described above, authenticated visitors of an Adobe CQ website can be targeted and provided relevant content based on obtained social profile data and their client context (i.e., provide a customized website tailored with respect to, or dynamically displayed/rendered in the context of the visitor). For example, an authenticated visitor whose Facebook® profile information matches a snowboarding segment can be displayed/rendered a snowboarding teaser upon logging into the Geometrixx Outdoors website using their Facebook® credentials.

In some embodiments an administrator can simulate how the website would be rendered in the context of various users and can view the social profile data for a specific user by configuring an existing client context by adding various social components (e.g., Facebook® interests, demographics, etc.) and then specifically loading the stored user's profile into the client context for the simulation and testing of various campaign segments and traits.

FIG. 10 is a flow diagram illustrating an embodiment of a process for obtaining social user profile data. In some embodiments, process 1000 is used to implement process step 902 of FIG. 9. The process begins at 1002 when an indication of a login to a digital identity platform by a user is received (e.g., user has logged into Geometrixx Outdoors via their existing Facebook® or Twitter® digital identity).

At 1004, the user is authenticated. The user can be authenticated via authentication configuration engine 202 of FIG. 2.

At 1006, authorization to access resources is requested. In some embodiments, if the user is a new user, they are prompted to indicate what resources the Adobe CQ website is authorized to access and obtain from an external digital identity platform. In some embodiments, the resources requested are specified in a previously generated application service configuration (e.g., basic/extended permissions (706) of FIG. 7A).

At 1008, an access token is received from an authentication provider/digital identity platform. The access token can be associated with a set of access permissions indicating the resources to which authorization has been granted (e.g., Facebook® likes, friends, interests, Twitter® followers, hash tags, etc.).

At 1010, user information is obtained. In some embodiments, user information is obtained from an authentication provider via the access token provided by the authentication provider. In some embodiments, user information is obtained via a graph API associated with an authentication provider (e.g., Facebook® social graph API). In some embodiments, the obtained user information/social profile data is stored with a user profile (e.g., Adobe CQ user profile). In some embodiments, the obtained user information/social profile data can be configured/specified to be stored using tags that can be stored in a tagging infrastructure. For example, “likes” and “interests” obtained from a user's Facebook® profile can be tagged and stored in a central Adobe CQ tagging infrastructure. Tags can then be taken advantage of and used throughout the Adobe CQ environment (e.g., by marketing campaign management component or any other appropriate CQ component) to determine what content should be targeted upon. Social profile data can be assigned to a particular tag and reused. For example, if a tag for “UC Berkeley” was previously stored in the tagging infrastructure, in the event that a new user logged in via Facebook® and was indicated to go to “UC Berkeley,” a new tag would not have to be created, and the profile of the user can be associated with the existing “UC Berkeley” tag. Information obtained for different digital identity platforms can also be grouped in various ways. For example, all tags generated from Facebook® and Twitter® information can be grouped into a single “social tags” bucket, with duplicates removed as needed, or the tags may remain separate and distinct from each other (e.g., one location for Facebook® tags, separate location for Twitter® tags). The grouping of information obtained for different digital identity platforms can be specified/implemented via authentication handler 208.

At 1012, a client context for the user is generated. In some embodiments, the client context includes a user profile generated using data (e.g., social profile data) obtained from external digital identity platforms. The user profile can be configured to display social profile data (e.g., age, favorite quote, books, likes, interests). The social profile data can be applied to the client context automatically or by an administrator of the Adobe CQ system. Tags can also be applied to the client context. As described above, the client context can reside in a browser of the Adobe CQ website visitor, with an Adobe CQ user profile for the visitor also stored on the side of the Adobe CQ system. Personalized content can be provided to the visitor based on their client context and user profile. In some embodiments, profile simulation can be performed for testing purposes by configuring a client context in different ways and loading and simulating a client context user profile on any page (e.g., in a web experience management system on an Adobe CQ system) to see what content will be provided to them.

Facebook®Facebook®Facebook®Facebook®FIG. 11 is a diagram illustrating an embodiment of an interface for logging in to an Adobe CQ website using existing digital identities. In the example shown, the visitor can login with one or more of their Facebook® digital identity, Twitter® identity, or Geometrixx Outdoors identity (e.g., if Adobe CQ website has internal mechanism for authentication/credentials). In some embodiments, the user is presented with additional prompts requesting authorization to resources (e.g., likes, favorites, interests, friends, etc.). In some embodiments, a first prompt for basic permissions is displayed to a user, and a second prompt that includes extended permissions is presented to a user. In some embodiments, the request for authorization to access resources is presented the first time a user has logged onto an Adobe CQ website. In some embodiments, a user profile is not stored in the event that a user does not complete the login procedure or only partially completes the login procedure (e.g., cancelling login before all prompts/requests have been accepted).

FIG. 12 is a diagram illustrating an embodiment of an interface for configuring a client context to display social profile data. In the example shown, various user information and social profile data display components can be added to the client context. For example, in the interface shown, Facebook® Interests component (1202) can be added to the client context via drag and drop (1204). Other social profile data components can also be added to the client context at the same time.

FIG. 13 is a diagram illustrating an embodiment of an interface for configuring a segment. In the example shown, a segment for snowboarding is being generated. Various rules/traits can be selected to define the segment. For example, traits associated with Facebook® interests (e.g., interest=snowboarding) can be added to the segment.

FIG. 14 is a diagram illustrating an embodiment of an interface for creating a teaser. In the example shown, the teaser leverages segments (1402) and social profile data. The teaser can be associated with a marketing campaign, managed by, for example, the marketing campaign management component of an Adobe CQ system.

Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive. 

What is claimed is:
 1. A system, comprising: a processor configured to: request social profile data for a user from an authentication provider using a token associated with the user; and generate a rule for web site customization using the social profile data; and a memory coupled to the processor and configured to provide the processor with instructions.
 2. The system of claim 1, wherein the processor is further configured to store the social profile data.
 3. The system of claim 2, wherein the social profile data is stored using tags.
 4. The system of claim 3, wherein the tags are generated based at least in part on the social profile data.
 5. The system of claim 1, wherein the processor is further configured to display targeted content based at least in part on the social profile data.
 6. The system of claim 1, wherein the processor is further configured to add the social profile data to a segment.
 7. The system of claim 1, wherein the targeted content comprises a teaser.
 8. A method, comprising: requesting social profile data for a user from an authentication provider using a token associated with the user; and generating a rule for web site customization using the social profile data.
 9. The method of claim 8, further comprising storing the social profile data.
 10. The method of claim 9, wherein the social profile data is stored using tags.
 11. The method of claim 10, wherein the tags are generated based at least in part on the social profile data.
 12. The method of claim 8, further comprising displaying targeted content based at least in part on the social profile data.
 13. The method of claim 8, further comprising adding the social profile data to a segment.
 14. The method of claim 8, wherein the targeted content comprises a teaser.
 15. A computer program product, the computer program product being embodied in a tangible computer readable storage medium and comprising computer instructions for: requesting social profile data for a user from an authentication provider using a token associated with the user; and generating a rule for web site customization using the social profile data.
 16. The computer program product recited in claim 15, further comprising computer instructions for: storing the social profile data.
 17. The computer program product recited in claim 16, wherein the social profile data is stored using tags.
 18. The computer program product recited in claim 17, wherein the tags are generated based at least in part on the social profile data.
 19. The computer program product of claim 15, further comprising computer instructions for: displaying targeted content based at least in part on the social profile data.
 20. The computer program product of claim 15, wherein the targeted content comprises a teaser. 